Printer for performing printing based on combined object data including two or more object data

ABSTRACT

A communication portion receives object data corresponding to an object. A processor receives a record including single object data and object names from an external device. The processor first stores the record and object names and first selects the object name having a predetermined configuration. The processor second selects, as at least two selected object data, at least two of the single object data, from the plurality of single object data included in the record, based on the configuration of the object name selected by the first selecting. The processor generates the combined object data that includes the at least two selected object data selected by the second selecting, as at least two setting object data. The processor second stores the generated combined object data. The processor prints a print image on the print medium, using the printing mechanism, based on the combined object data.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to Japanese Patent Application No.2014-113166 filed on May 30, 2014, the disclosure of which is hereinincorporated by reference in its entirety.

BACKGROUND

The present disclosure relates to a printer.

A printer is known that is capable of generating a label by performingprinting on a tape. In this type of printer, a function is known thatprints on the tape based on a plurality of items respectively includedin a plurality of records of a database imported from an externaldevice. The items are hereinafter referred to as object data, and aprint target image (a character string, etc.) that is to be printed onthe tape based on the object data is referred to as an object. Examplesof categories of the object data include “Product code,” “Product name,”“Price” and “Barcode” etc. In known technology, technology is disclosedthat determines whether printing by the printer is possible based on aCSV file having the extension “csv” and transmits a CSV file to aprinter when printing is possible. The printer that has received the CSVfile transmitted using this technology prints the object on the tapebased on a plurality of object data respectively included in a pluralityof records of the CSV file.

SUMMARY

In the printer, a demand occurs in which it is desired to generate newobject data (hereinafter referred to as combined object data) in whichtwo or more of the received plurality of object data are combined. Forexample, there is a case in which it is desired to combine therespective object data of the categories “Product code” and “Price” andgenerate the combined object data by which the “Barcode” can be printedusing the printer. As an example of this type of case, a case can begiven in which at least one of the plurality of object data included inthe combined object data is edited by the printer. In this case, it isnecessary for the combined object data that includes the edited objectdata to be similarly edited, and it is preferable for the combinedobject data to be generated in the printer.

However, in the above-described case, based on the CSV file, it is notpossible to identify how two or more of the object data are selectedfrom the plurality of object data of the received CSV file and how thecombined object data is thereby generated. Therefore, in order togenerate the combined object data in the printer, it is necessary for auser to set, on the printer, the two or more object data to be includedin the combined object data. In this case, time and effort are requiredfor the user to perform the operation, and it is not possible for theprinter to easily perform printing based on the combined object data.

Various embodiments of the general principles described herein provide aprinter that is capable of easily performing printing based on combinedobject data that includes two or more object data.

Embodiments herein provide a printer configured to print a print imagehaving a plurality of objects onto a print medium. The printer includesa communication portion, a storage portion, a printing mechanism and aprocessor. The communication portion is provided to receive a pluralityof object data from an external device. Each of the plurality of objectdata corresponds to each of a plurality of objects. The storage portionis configured to store at least the plurality of object data. Theprinting mechanism is provided to form the print image on the printmedium. The processor is provided to control the communication portion,the storage portion and the printing mechanism.

The processor receives at least a record and a plurality of object namesfrom the external device. The record includes a plurality of singleobject data. The plurality of object names are names respectivelycorresponding to the plurality of single object data. The single objectdata is the object data other than combined object data. The combinedobject data is the object data in which at least two of the singleobject data are combined. The processor first stores, in the storageportion, the record and the plurality of object names received by thereceiving. The processor first selects the object name having apredetermined configuration, from the plurality of object names storedin the storage portion. The processor second selects, as at least twoselected object data, at least two of the single object data, from theplurality of single object data included in the record stored in thestorage portion, based on the configuration of the object name selectedby the first selecting. The processor generates the combined object datathat includes the at least two selected object data selected by thesecond selecting, as at least two setting object data. The processorsecond stores, in the storage portion, the generated combined objectdata. The processor prints a print image on the print medium, using theprinting mechanism, based on the combined object data stored in thestorage portion.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be described below in detail with reference to theaccompanying drawings in which:

FIG. 1 is a diagram showing an overview of a printing system and anelectrical configuration of a printer and a PC;

FIG. 2 is a diagram showing an editing screen displayed on a displayportion of the PC;

FIG. 3 is a diagram showing a barcode;

FIG. 4 is a diagram showing template data;

FIG. 5 is a diagram showing an editing screen displayed on a displayportion of the printer;

FIG. 6 is a diagram showing a one-touch panel;

FIG. 7 is a flowchart of PC-side main processing;

FIG. 8 is a flowchart of printer-side first main processing;

FIG. 9 is a flowchart of printer-side second main processing;

FIG. 10 is a flowchart of printer-side third main processing;

FIG. 11 is a flowchart of template switching processing;

FIG. 12 is a flowchart of template load processing;

FIG. 13 is a flowchart of DB load processing;

FIG. 14 is a flowchart of object data setting processing;

FIG. 15 is a flowchart of combined object check processing;

FIG. 16 is a flowchart of combined object value setting processing;

FIG. 17 is a flowchart of main editing processing;

FIG. 18 is a flowchart of idle screen processing;

FIG. 19 is a flowchart of record selection screen processing;

FIG. 20 is a flowchart of field selection screen processing;

FIG. 21 is a flowchart of object editing screen processing;

FIG. 22 is a flowchart of data editing processing;

FIG. 23 is a flowchart of combined object editing processing;

FIG. 24 is a flowchart of specific field replacement processing;

FIG. 25 is a flowchart of combined object search/replacement processing;and

FIG. 26 is a flowchart of combined object value replacement processing.

DETAILED DESCRIPTION

An overview of a printing system 1 will be explained with reference toFIG. 1. The printing system 1 is provided with a printer 4 and a PC 5.The printer 4 and the PC 5 are connected via a cable 3. The printer 4and the PC 5 can communicate via the cable 3.

The printer 4 is configured such that a tape cassette (not shown in thedrawings) can be mounted therein. The printer 4 is a tape printer thatcan perform printing (form a plurality of dots) on a tape that is fedout from the tape cassette and thus create a label. The printer 4receives a DB file 432 (refer to FIG. 2) that is shown in acomma-separated values (CSV) format, and template data 431 (refer toFIG. 4) from the PC 5. DB is an abbreviation of database. The DB file432 that is shown in the CSV format is hereinafter referred to as a “CSVfile of the DB file 432” or simply as the “CSV file.” The printer 4performs template printing based on the received template data 431 andCSV file. The template printing will be explained in detail later. ThePC 5 generates and edits the template data 431 and the DB file 432 thatis the basis of the CSV file in accordance with an input operation on aninput portion 56. The PC 5 can transmit the template data 431 and theCSV file to the printer 4 and cause the printer 4 to perform thetemplate printing.

An electrical configuration of the printer 4 will be explained. Theprinter 4 is provided with a CPU 41, a RAM 42, a flash ROM 43, an EEPROM44, a communication portion 45, an input portion 46, a display portion47, a thermal head 48 and a roller 49. The CPU 41 executes control ofthe printer 4. The CPU 41 is electrically connected to the RAM 42, theflash ROM 43, the EEPROM 44, the communication portion 45, the inputportion 46, the display portion 47, the thermal head 48 and the roller49. Various temporary data are stored in the RAM 42. Programs used bythe CPU 41 to execute control of the printer 4 are stored in the flashROM 43. Further, the template data 431 and the CSV file received fromthe PC 5 are stored in the flash ROM 43. Dot pattern data for printingused to print various characters and barcodes are categorized by fontand size and stored in the EEPROM 44. The communication portion 45 is acontroller that is used to perform communication with the PC 5. Theinput portion 46 is a touch panel. The display portion 47 is an LCD. Thethermal head 48 emits heat in response to a signal from the CPU 41 andperforms printing on a tape. The roller 49 is a tape feed roller thatfeeds the tape.

An electrical configuration of the PC 5 will be explained. The PC 5 isprovided with a CPU 51, a RAM 52, a ROM 53, an HDD 54, a communicationportion 55, the input portion 56 and a display portion 57. The CPU 51executes control of the PC 5. The CPU 51 is electrically connected tothe RAM 52, the ROM 53, the HDD 54, the communication portion 55, theinput portion 56 and the display portion 57. Various temporary data arestored in the RAM 52. A BIOS and the like are stored in the ROM 53.Programs used by the CPU 51 to execute control of the PC 5, and an OSare stored in the HDD 54. Further, the template data 431 and the DB file432 are stored in the HDD 54. The communication portion 55 is acontroller to perform communication with the printer 4. The inputportion 56 is a keyboard and a mouse. The display portion 57 is an LCD.

An editing screen 571 that is displayed on the display portion 57 willbe explained with reference to FIG. 2. A template 20 shows a print imagethat is to be printed on the tape by the printer 4. Printing based onthe template 20 is referred to as template printing. The editing screen571 is displayed when an application that allows creation and editing ofthe template 20 is executed by the CPU 51 of the PC 5. The editingscreen 571 includes a first area 571A, a second area 571B and a thirdarea 571C. Each of these will be explained below.

The template 20 is displayed in the first area 571A. The template 20 isformed by arranging a plurality of objects (“22A” etc. in FIG. 2) insidea specific area 21. The “objects” are print target images (a characterstring and the like) to be printed on a label created in accordance withthe template 20. In the case of FIG. 2, the object 22A that includes acharacter string “Pork back ribs,” an object 22B that includes a barcode221, an object 22C that includes a character string “Price (yen)” and anobject 22D that includes numerals “300” are arranged inside the area 21.In accordance with an input operation on the input portion 56, the CPU51 can change the category of the objects arranged inside the area 21,move the positions of the objects 22A to 22D arranged inside the area 21and so on. Thus, by performing an input operation on the input portion56 while viewing the template 20, a user can adjust the print image tobe printed on the tape.

Note that the barcode 221 that is included in the object 22B is a code(an in-store code) that a store or the like can freely designate. Forexample, the in-store code is used for price lists for fresh foodproducts, membership authentication for point cards and so on. Thein-store code is used only in that store and is not shared by anotherstore. As shown in FIG. 3, the barcode 221 includes a category 221A “20”of a target product, a product code 221B “12345” and a price 221C“00300.”

As shown in FIG. 2, a character string, numerals, a barcode and a nameof each of the objects (hereinafter referred to as an object name)included respectively in the objects 22A to 22D arranged in the area 21of the template 20 are displayed in the second area 571B. In the case ofFIG. 2, “Pork back ribs” and the object name “Product name”corresponding to the object 22A, the barcode 221 and the object name“_AABBBBBDDDDD_” corresponding to the object 22B, “Price (yen)” and theobject name “Label 1” corresponding to the object 22C, and “300” and theobject name “Price” corresponding to the object 22D are displayed. Theobject names are set by the user when the objects included in the area21 of the template 20 are set by the user.

A table 40, which shows the DB file 432 that can be linked to thetemplate 20, is displayed in the third area 571C. In the topmost row ofthe table 40, “A,” “B,” “C,” “D” and “E” are respectively information(hereinafter referred to as a “field ID”) that identifies respectivecorresponding columns (hereinafter also referred to as “fields”) of theDB file 432. “Category,” “Code,” “Item,” “Price” and “Barcode” that areto the lower side of the field IDs respectively show names of the fields(hereinafter also referred to as “field names”). The leftmost column(“1,” “2,” “3”) shows row numbers. The data of the DB file 432 for onerow corresponds to a record. A triangle allocated to the row number “1”indicates that the record of the corresponding row number is selected.By performing an operation, on the input portion 56, to select aspecific field of a specific record and input a value, the user canchange the specific data of the DB file 432.

In the meantime, of the DB file 432, data of the field ID “E” (the fieldname “Barcode”) is generated by combining, in order, two digits of dataof the field ID “A” (the field name “Category”), 5 digits of data of thefield ID “B” (the field name “Code”) and 5 digits of data of the fieldID “D” (the field name “Price”). Thus, for example, if the data of therow number “1” and the field ID “D” (the field name “Price”) is changedfrom “300” to “450,” the CPU 51 changes the data of the row number “1”and the field ID “E” (the field name “Barcode”) from “201234500300” to“201234500450.”

The user can perform settings to link a specific field of the DB file432 to the objects 22A to 22D included in the area 21 of the template20. In the case of FIG. 2, the field ID “C” (the field name “Item”) ofthe DB file 432 is linked to the object 22A (the object name “Productname”). The field ID “E” (the field name “Barcode”) of the DB file 432is linked to the object 22B (the object name “_AABBBBBDDDDD_”). Thefield ID “D” (the field name “Price”) of the DB file 432 is linked tothe object 22D (the object name “Price”).

An example will be given of a case in which the data of the template 20that is set in the above-described manner (hereinafter referred to asthe “template data 431”) and the CSV file of the DB file 432 aretransmitted to the printer 4. In this case, the CPU 41 of the printer 4stores the received template data 431 and the CSV file in the flash ROM43. Based on the template data 431, the CPU 41 can generate a pluralityof print images in which, of the CSV file, each of a plurality of datacorresponding to the field ID “C” is arranged in the position of theobject 22A, each of a plurality of data corresponding to the field ID“E” is arranged in the position of the object 22B and each of aplurality of data corresponding to the field ID “D” is arranged in theposition of the object 22D. As a result, by using the template printing,the user can cause the printer 4 to print a plurality of differing printimages, simply by creating the single template 20 using the PC 5.

More specifically, a first print image is generated in which “Pork backribs,” “201234500300 (barcode)” and “300” corresponding to the rownumber “1” and the field IDs “C,” “E” and “D” are arranged in thepositions of the objects 22A, 22B and 22D inside the area 21. Further, asecond print image is generated in which “Sirloin,” “211234600450(barcode)” and “450” corresponding to the row number “2” and the fieldIDs “C,” “E” and “D” are arranged. In addition, a third print image isgenerated in which “Chicken thighs,” “301234700198 (barcode)” and “198”corresponding to the row number “3” and the field IDs “C,” “E” and “D”are arranged.

Hereinafter, each of the plurality of data included in the CSV file isreferred to as the “object data.” The object data in which the pluralityof object data are combined (namely, the object data of the field ID“E”) is referred to as the “combined object data” and the other objectdata (the object data of the field IDs “A” to “D”) are referred to as“single object data.” Each of the objects (the objects 22A and 22D)linked to the single object data is referred to as a “single object.”The object (the object 22B) linked to the combined object data isreferred to as a “combined object.”

FIG. 4 shows the template data 431 that is transmitted to the printer 4from the PC 5. The single template data 431 is created in accordancewith the template 20 created via the editing screen 571 (refer to FIG.2). The template data 431 includes a template name, a template number, abackground image, a paper format, a DB file name and a plurality ofpieces of object information. The plurality of pieces of objectinformation correspond to the number of the objects 22A to 22D includedin the area 21 of the template 20. The pieces of object informationrespectively include the object name, a category, anarrangement/size/font, an initial value and the field ID. Hereinafter,the plurality of pieces of object information are respectively referredto as pieces of object information [0] to [N−1] (N is a maximum numberof the pieces of object information, and in the case of the template 20shown in FIG. 2, N=4).

The template name is a name of the template data 431. The templatenumber is an identification number indicating the template data 431. Thetemplate number is a value that is assigned each time the template data431 is created by the PC 5, starting from 1 and adding 1 each time. Thebackground image shows a background image of the print image that isgenerated based on the template data 431. The paper format indicates atype of tape on which the print image is to be printed. The DB file nameis a file name of the CSV file of the DB file 432 that is linked to theobjects 22A, 22B and 22D of the template 20.

The respective pieces of object information [0] to [N−1] includeinformation corresponding to the objects 22A to 22D, respectively. Thecategory indicates a category of the corresponding object. Specificexamples of the category of the object include “Date,” “Price,” “Productname,” “Barcode” and “Graphic” etc. The arrangement indicates theposition of the object inside the area 21. The size indicates a size ofthe object. The font indicates a font of the character string andnumerals when the data included in the object is a character string ornumerals. The initial value indicates an initial value of the object.The field ID indicates the field ID of the linked field, of the CSV fileof the DB file 432. Note that the field ID is not included in the objectinformation corresponding to the object 22C, for which the link is notset.

The printer 4 has a function to edit CSV data stored in the flash ROM43. An editing screen 60 (refer to FIG. 5) that is displayed on thedisplay portion 47 when the editing of the CSV file is performed by theprinter 4 will be explained. Hereinafter, it is assumed that a pluralityof the template data 431 and the CSV data linked to the plurality oftemplate data 431 are received and stored in the flash ROM 43.

It should be noted that, when the editing of the CSV file is performedby the printer 4, a one-touch panel 68 shown in FIG. 6 is placed on theinput portion 46 (refer to FIG. 1). A plurality of command buttons 68A(“BACK,” “UP,” “DOWN,” “OK” and “PRINT” buttons) and ten-key buttons 68B(“0” to “9” buttons) are drawn on the one-touch panel 68. In a state inwhich the one-touch panel 68 is placed on the input portion 46, when theuser performs a touch operation from the upper side of the one-touchpanel 68, the input portion 46 can detect a position that has beentouched. Based on the position detected by the input portion 46 and thepositions of the plurality of command buttons 68A and the ten-keybuttons 68B on the one-touch panel 68, the CPU 41 can identify which ofthe plurality of buttons has been touched.

As shown in FIG. 5, as the editing screen 60, one of an idle screen 61,a record selection screen 62, a field selection screen 63 and an objectediting screen 64 is displayed. A template number 60A, a template name60B, a row number 60C and an object data 60D are included in each of thescreens. As the template number 60A and the template name 60B, thetemplate number and the template name of one of the plurality oftemplate data 431 stored in the flash ROM 43 are displayed. As the rownumber 60C, a number of a specific row from a plurality of rows when theCSV file is shown in a tabular format is displayed. As the object data60D, one of the plurality of object data of the row of the CSV fileindicated by the row number is displayed.

Hereinafter, the “row (or record) when the CSV file is shown in thetabular format” can be referred to as the “row (or record) of the CSVfile.” The “column (or field) when the CSV file is shown in the tabularformat” can be referred to as the “column (or field) of the CSV file.”As IDs that identify each of the plurality of columns of the CSV file,the field IDs are used. “A,” “B”, “C” . . . , or “1,” “2,” “3” . . . aredisplayed as the field IDs. The field IDs “A” and “1,” “B” and “2,” and“C” and “3” . . . each indicate a column of the same CSV file.

When the editing of the CSV file is started, first, the idle screen 61is displayed on the display portion 47. On the idle screen 61, aninitial value “01” is displayed as the template number 60A and aninitial value “00001” is displayed as the row number 60C. Further, atemplate name “Meat,” which corresponds to the initial value “01” of thetemplate number 60A, is displayed as the template name 60B. Object data“20” (refer to FIG. 2) that corresponds to the row number “1” and thefield ID “A” of the CSV file is displayed as the object data 60D.

The idle screen 61 is a screen on which the template number 60A can beselected. In the case of the idle screen 61, in order to indicate thatthe template number 60A can be selected, the template number 60A isunderlined. Further, to the left side of the template number 60A, anarrow 61A is displayed that indicates that the template number 60A canbe selected. In this state, when the “DOWN” button is touched by theuser, the template number 60A is changed from “01” to “02.” In thiscase, the template name 60B changes to the template name correspondingto the template number 60A “02” following the change. The initial value“00001” is displayed as the row number 60C. Object data that correspondsto the row number “1” and the field ID “A” of the CSV file is displayedas the object data 60D.

If the “OK” button is touched in a state in which the idle screen 61 isdisplayed, the record selection screen 62 is displayed. The recordselection screen 62 is a screen on which the row number 60C can beselected. In the case of the record selection screen 62, in order toindicate that the row number 60C can be selected, the row number 60C isunderlined. Further, to the left side of the row number 60C, an arrow62A is displayed that indicates that the row number 60C can be selected.In this state, when the “DOWN” button is touched by the user, the rownumber 60C is changed from “00001” to “00002.” In this case, thetemplate number 60A “01” and the template name 60B “Meat” are notchanged. Object data “21” (refer to FIG. 2) that corresponds to the rownumber “2” and the field ID “A” of the CSV file is displayed as theobject data 60D.

If the “OK” button is touched in the state in which the record selectionscreen 62 is displayed, the field selection screen 63 (specifically,field selection screens 63A to 63E) is displayed. The field selectionscreen 63 is a screen on which the field ID can be selected. If the“DOWN” button is touched by the user in the state in which the fieldselection screen 63A is displayed, the field column is changed from “A”to “B.” In this case, the template number 60A “01,” the template name60B “Meat” and the row number 60C “00001” are not changed. Single objectdata “12345” (refer to FIG. 2) that corresponds to the row number “1”and the field ID “B” of the CSV file is displayed as the object data 60D(the field selection screen 63B). If the “DOWN” button is touched by theuser in the state in which the field selection screen 63B is displayed,the field column is changed from “B” to “C.” The object data “Pork backribs” (refer to FIG. 2) that corresponds to the row number “1” and thefield ID “C” of the CSV file is displayed as the object data 60D (thefield selection screen 63C).

Each time the “DOWN” button is touched by the user, the field column ischanged in sequence to “D” and to “E.” As the object data 60D, theobject data “300” (the field selection screen 63D) (refer to FIG. 2)that corresponds to the row number “1” and the field ID “D” of the CSVfile and the object data “201234500300” (the field selection screen 63E)(refer to FIG. 2) that corresponds to the row number “1” and the fieldID “E” are displayed.

An example will be given of a case in which the “OK” button is touchedin the state in which the field selection screen 63D is displayed. Inthis case, the object editing screen 64 is displayed. The object editingscreen 64 is a screen that is used to edit the object data of the CSVfile that is displayed as the object data 60D. In the case of the objectediting screen 64, in order to indicate that the object data 60D can beedited, the object data 60D is underlined.

A case will be explained in which the “3,” “2” and “0” buttons aretouched in sequence. “300” that is displayed as the object data 60D onthe object editing screen 64 is changed to “320.” If the “OK” button istouched in this state, a field selection screen 63F is displayed.Further, the object data that corresponds to the row number “1” and thefield ID “D” of the CSV file is changed from “300” to “320.” On thefield selection screen 63F, “320” following the change is displayed asthe object data 60D.

In this case, it should be noted that the object data corresponding tothe field ID “E” of the CSV file is combined object data that isgenerated by combining the single object data of the field IDs “A,” “B,”and “D.” Therefore, when the object data of the field ID “D” is changedfrom “300” to “320,” the object data of the field ID “E” also needs tobe changed from “201234500300” to “201234500320.” However, informationthat indicates that the object data of the field ID “E” is the combinedobject data is not included in the CSV file. Therefore, the CPU 41cannot identify the combined object data based on the CSV file itself.

In contrast to this, based on the configuration of the object name“_AABBBBBDDDDD_” of the object 22B that is linked with the field ID “E”of the CSV file, the CPU 41 of the present embodiment determines thatthe corresponding object is the combined object. More specifically, theCPU 41 identifies the object name of the object linked with the objectdata that is the target of editing in the CSV file, and when theidentified object name starts and ends with “_”, the CPU 41 determinesthat the corresponding object is the combined object.

In addition, based on the configuration of the object name“_AABBBBBDDDDD_”, the CPU 41 determines the respective fields of theplurality of single object data that form the basis of the combinedobject data. More specifically, the following is performed. The CPU 41extracts the configuration “AABBBBBDDDDD” of the object name, excludingthe “_”. Of the extracted configuration, the first and second charactersfrom the start both match the field ID “A” and the CPU 41 thereforedetermines that the first and second characters of the combined objectdata correspond to the single object data of the field ID “A” in the CSVfile. Further, the third to seventh characters all match the field ID“B” and the CPU 41 therefore determines that the third to seventhcharacters of the combined object data correspond to the single objectdata of the field ID “B” in the CSV file. In addition, the eighth totwelfth characters all match the field ID “D” and the CPU 41 thereforedetermines that the eighth to twelfth characters of the combined objectdata correspond to the single object data of the field ID “D” in the CSVfile.

By performing the determination in the above-described manner, the CPU41 can generate the combined object data that reflects a change contentwhen one of the plurality of single object data that is the basis of thecombined object data is changed. Further, as will be explained in detaillater, the CPU 41 can also reflect a change content in the plurality ofsingle object data that form the basis of the combined object data whenthe combined object data is changed. The user can cause the printer 4 torecognize the combined object data of the CSV file, by determining, inaccordance with the above-described rules, the object name that can beset for each object via the editing screen 571.

Note that the function to set the object names of the objects 22A to 22Dincluded in the template 20, is incorporated in a known application thatcan create the template 20. Further, the object names are normallyincluded in the object information of the template data that istransmitted to the printer 4 from the PC 5. Therefore, the CPU 41 of theprinter 4 can recognize the combined object data based on the templatedata corresponding to the template 20 that is created directly using theknown application. As a result, when the user causes the printer 4 torecognize the combined object data, the known application can be useddirectly and it is not necessary to use a special application.

Processing performed by the CPU 51 of the PC 5 will be explained withreference to FIG. 7. In the following explanation, “S” is anabbreviation of “step.” PC-side main processing is started by the CPU 51executing a program stored in the HDD 54 when an operation has beendetected, via the input portion 56, to transmit the template data 431 ofthe template 20 created via the editing screen 571 (refer to FIG. 2) andthe CSV file of the DB file 432 to the printer 4.

Processing at S1 is as follows. The CPU 51 acquires the name of thetemplate 20 created via the editing screen 571 as the template name. TheCPU 51 acquires the number of the created template 20 as the templatenumber. The CPU 51 acquires the background image of the set area 21 asthe background image. The CPU 51 acquires the type of the tape that isthe set printing target as the paper format. The CPU 51 stores theacquired template name, template number, background image and paperformat in the RAM 52.

The CPU 51 acquires a file name of the CSV file of the DB file 432linked to the template 20 as the DB file name (S3). The CPU 51 storesthe acquired DB file name in the RAM 52.

The CPU 51 acquires the pieces of object information respectivelycorresponding to the objects 22A to 22D included in the template 20(S5). More specifically, the following processing is performed. The CPU51 acquires “Product name,” “_AABBBBBDDDDD_”, “Label 1” and “Price” asthe object names corresponding to the objects 22A to 22D. The CPU 51acquires “Character string,” “Barcode,” “Character string” and “Monetaryamount” as the categories corresponding to the objects 22A to 22D. TheCPU 51 acquires coordinate information that can identify the positionsof the objects 22A to 22D inside the area 21 (refer to FIG. 2) as thearrangement corresponding to the objects 22A to 22D. The CPU 51 acquireslengths in the vertical and horizontal directions of the objects 22A to22D as the sizes corresponding to the objects 22A to 22D. The CPU 51acquires fonts of “Pork back ribs,” “Price (yen)” and “300” included inthe objects 22A, 22C and 22D as the fonts corresponding to the objects22A, 22C and 22D. The CPU 51 acquires “Pork back ribs,” “201234500300(barcode),” “Price (yen)” and “300” included in the objects 22A to 22Ddisplayed in the first area 571A as the initial values corresponding tothe objects 22A to 22D. The CPU 51 acquires the field IDs “C,” “E” and“D” as the field IDs corresponding to the objects 22A, 22B and 22D. TheCPU 51 stores the pieces of object information [0] to [N−1 (N=4)] of theacquired objects 22A to 22D in the RAM 52.

The CPU 51 reads out, from the RAM 52, the above-described data acquiredby the processing at S1, S3 and S5. The CPU 51 creates the template data431 (refer to FIG. 4) that includes the data read out from the RAM 52(S7). The CPU 51 creates the CSV file of the DB file 432 (refer to FIG.2) (S7). The CPU 51 transmits the created template data 431 and CSV fileto the printer 4 via the cable 3 (S9). The CPU 51 ends the PC-side mainprocessing.

Printer-side first main processing (refer to FIG. 8), printer-sidesecond main processing (refer to FIG. 9) and printer-side third mainprocessing (refer to FIG. 10 to FIG. 26) will be explained withreference to FIG. 8 to FIG. 26. The printer-side first main processing,the printer-side second main processing and the printer-side third mainprocessing are executed in parallel by the CPU 41 of the printer 4. Inthe following explanation, it is assumed that a plurality of thetemplate data (template number “1,” “2,” . . . ) and the one CSV fileare stored in the flash ROM 43. Further, it is assumed that the filename of the one CSV file is included as the DB file name of all theplurality of template data.

In the printer-side first main processing to the printer-side third mainprocessing, the CPU 41 uses integer type variables Tnum, Rnum andObjNum, state information and flag information stored in the RAM 42.Tnum indicates the template number selected by the “UP” and “DOWN”buttons being touched. Rnum indicates the row number selected by the“UP” and “DOWN” buttons being touched. ObjNum indicates, by a number,the field ID selected by the “UP” and “DOWN” buttons being touched.Depending on a state of the printer-side third main processing, one ofidle “0,” record selection “1,” field selection “2” and object editing“3” is set as the state information. Further, the CPU 41 usesinteger-type variables num, Digit, FiedNum, Fnum, count1, count2,count3, count4, count5 and count6 that are stored in the RAM 42. Inaddition, the CPU 41 uses character-type variables Result, ObjName,Char, TempValue and fval that are stored in the RAM 42.

Furthermore, as will be explained in detail later, as a character-typevariable, “object information [m]. object data (m=0, 1, . . . N−1)” isstored in the RAM 42. Object data is stored for each of the objects, asthe “object information [m]. object data (m=0, 1, . . . N−1)”. The“object information [m]. object data (m=0, 1, . . . N−1)” is referred towhen the print image is created.

Hereinafter, the template data of the template number Tnum is referredto as the template data [Tnum]. The record of the row number Rnum in theCSV file is referred to as the record [Rnum]. Of the CSV file read fromthe flash ROM 43 and stored in the RAM 42, the object data of the rownumber Rnum and the field ID ObjNum is referred to as CSV [Rnum][ObjNum]. When two of the field IDs are a target of comparison, “A” and“1,” “B” and “2” and “C” and “3” etc. are respectively determined to bethe same.

The printer-side first main processing performed by the CPU 41 of theprinter 4 will be explained with reference to FIG. 8. The printer-sidefirst main processing is processing to receive the template data 431 andCSV file transmitted from the PC 5 and store them in the flash ROM 43.The printer-side first main processing is started by the CPU 41executing a program stored in the flash ROM 43, when the template data431 and the CSV file are transmitted from the PC 5 connected via thecable 3. The CPU 41 receives the template data 431 and the CSV filetransmitted from the PC 5 (S11). The CPU 41 stores the received templatedata 431 and CSV file in the flash ROM 43 (S13). The CPU 41 ends theprinter-side first main processing.

The printer-side second main processing that is performed by the CPU 41of the printer 4 will be explained with reference to FIG. 9. Theprinter-side second main processing is processing that causes theediting screen 60 (refer to FIG. 5) to be displayed on the displayportion 47, based on Tnum, Rnum, ObjNum and the state information. Theprinter-side second main processing is started by the CPU 41 executing aprogram stored in the flash ROM 43, when an operation to start theediting of the CSV file is performed via the input portion 46.

The CPU 41 causes the editing screen 60 to be displayed on the displayportion 47 in accordance with the state information (S87). Specifically,the CPU 41 displays the idle screen 61 when the state information isidle “0.” The CPU 41 displays the record selection screen 62 when thestate information is record selection “1.” The CPU 41 displays the fieldselection screen 63 when the state information is field selection “2.”The CPU 41 displays the object editing screen 64 when the stateinformation is object editing “3.”

The CPU 41 displays Tnum as the template number 60A. As the templatename 60B, the CPU 41 displays the template name included in the templatedata (the template data [Tnum]) that has been read out from the flashROM 43 and stored in the RAM 42. The CPU 41 displays Rnum as the rownumber 60C (S88). The CPU 41 displays CSV [Rnum] [ObjNum] as the objectdata 60D (S89).

The CPU 41 determines whether or not an operation to end the editing ofthe CSV file has been performed via the input portion 46 (S90). When theCPU 41 determines that the operation to end the editing has not beenperformed (no at S90), the CPU 41 returns the processing to S87. Whenthe CPU 41 determines that the operation to end the editing has beenperformed (yes at S90), the CPU 41 ends the printer-side second mainprocessing.

The printer-side third main processing that is performed by the CPU 41of the printer 4 will be explained with reference to FIG. 10 to FIG. 26.The printer-side third main processing is started by the CPU 41executing a program stored in the flash ROM 43, when an operation tostart the editing of the CSV file is performed via the input portion 46.

The CPU 41 initializes Tnum, Rnum and ObjNum by setting them to 1 (S21).The reason for the initialization is to display the template number 60A“01 (=Tnum),” the row number 60C “00001 (=Rnum)” and the object data 60D“CSV [1 (=Rnum)] [1 (=ObjNum)]” on the first screen (the idle screen 61,refer to FIG. 5) of the editing screen 60.

The CPU 41 performs template switching processing (S23). The templateswitching processing is processing to acquire the template data [Tnum]and to acquire, from the CSV file, the object data (“object information[0]. object data” to “object information [N−1]. object data”)respectively corresponding to the pieces of object information [0] to[N−1] of the template data [Tnum].

The template switching processing will be explained with reference toFIG. 11. In order to acquire the template data [Tnum], the CPU 41performs template load processing (S31).

The template load processing will be explained with reference to FIG.12. The CPU 41 reads the template data [Tnum] from the flash ROM 43 andstores the template data [Tnum] in the RAM 42 (S41). The CPU 41initializes Rnum and ObjNum by setting them to 1 (S43). The reason forthe initialization is to constantly display CSV [1 (=Rnum)] [1(=ObjNum)] as the object data 60D of the editing screen 60, when Tnum ischanged and the template data is newly read out (for example, when thetemplate switching processing is performed by processing at S141 (referto FIG. 18)). The CPU 41 ends the template load processing and returnsthe processing to the template switching processing (refer to FIG. 11).

As shown in FIG. 11, after performing the template load processing bythe processing at S31, the CPU 41 performs DB load processing (S35). TheDB load processing is processing to acquire the object datacorresponding to the field IDs included respectively in the pieces ofobject information [0] to [N−1] of the template data [Tnum], of the dataof the record [Rnum] of the CSV file.

The DB load processing will be explained with reference to FIG. 13. TheCPU 41 initializes ObjNum by setting it to 1 (S51). The CPU 41 reads outthe CSV file stored in the flash ROM 43 and stores it in the RAM 42(S53). The CPU 41 selects the record [Rnum] of the CSV file stored inthe RAM 42 (S55). The CPU 41 performs object data setting processing(S57). The object data setting processing is processing to decide, basedon the record [Rnum] selected at S55, the object data corresponding tothe field IDs respectively included in the pieces of object information[0] to [N−1] of the template data [Tnum].

The object data setting processing will be explained with reference toFIG. 14. The CPU 41 sets count1 to 0 (S61). The CPU 41 determineswhether or not the number N of the pieces of object information [0] to[N−1] of the template data [Tnum] is larger than count1 (S63). When theCPU 41 determines that the number N of the pieces of object information[0] to [N−1] is larger than count1 (yes at S63), the CPU 41 determineswhether or not the field ID is included in the object information[count1] (S65).

When the CPU 41 determines that the field ID is included (yes at S65),the CPU 41 performs combined object check processing (refer to FIG. 15),in order to determine whether or not the object corresponding to theobject information [count1] is the combined object (S67). The objectname included in the object information [count1] is set as a parameterfor the combined object check processing.

The combined object check processing will be explained with reference toFIG. 15. The CPU 41 determines whether or not the object name of theparameter starts and ends with “_” (S81). When the CPU 41 determinesthat the object name starts and ends with “_” (yes at S81), the CPU 41determines that the object corresponding to the object name is thecombined object. The CPU 41 stores the flag information “0,” whichindicates that the object is the combined object, in the RAM 42 (S83).The CPU 41 returns the processing to the object data setting processing(refer to FIG. 14).

When the CPU 41 determines that the object name does not start and endwith “_” (no at S81), the CPU 41 determines that the objectcorresponding to the object name is not the combined object. The CPU 41stores the flag information “−1,” which indicates that the object is notthe combined object, in the RAM 42 (S85). The CPU 41 returns theprocessing to the object data setting processing (refer to FIG. 14).

As shown in FIG. 14, after performing the combined object checkprocessing (S67), based on the flag information stored in the RAM 42,the CPU 41 determines whether or not the object corresponding to theobject information [count1] is the combined object (S71). When the flaginformation “0” is stored, the CPU 41 determines that the objectcorresponding to the object information [count1] is the combined object(yes at S71). In order to generate the combined object data, the CPU 41performs combined object value setting processing (refer to FIG. 16)(S73). The object name is set as a parameter for the combined objectvalue setting processing.

The combined object value setting processing will be explained withreference to FIG. 16. The CPU 41 sets “0x00” as Result and thusinitializes Result (S91). The CPU 41 sets a character code of the objectname of the parameter as ObjName (S93). The CPU 41 deletes “0x5F” whichis the character code of “_” at the start and the end of ObjName (S95).The CPU 41 sets count2 to “0” (S97). The CPU 41 determines whether ornot a number of character codes included in ObjName is greater thancount2 (S99). When the CPU 41 determines that the number of charactercodes included in ObjName is greater than count2 (yes at S99), the CPU41 advances the processing to S101.

Of ObjName, the CPU 41 sets the character code of “count2” (hereinafterreferred to as ObjName(count2)) as Char (S101). When the same charactercode as the character code of ObjName(count2) continues from“count2+1”th onward, the CPU 41 identifies a number for which the samecharacter code continues (hereinafter referred to as a continuousnumber). The CPU 41 sets the identified continuous number as Digit(S103). The CPU 41 subtracts the character code “0x41” of “A” from Char.The CPU 41 sets a result of the subtraction as the variable FiedNum(S105). Note that when Char is “A (0x41),” for example, FiedNum is “0,”when Char is “B (0x42),” FiedNum is “1” and when Char is “C (0x43),”FiedNum is “2.

The CPU 41 selects the object data of CSV [Rnum] [FiedNum] and addscharacters to the start so that a number of digits matches Digit (S106).For example, when the object data of CSV [Rnum] [FiedNum] is numerals,“0” is added to the start of the object data. The CPU 41 adds the objectdata, for which the number of digits has been adjusted to match Digit,to the end of Result (S107). The CPU 41 adds Digit to count2 and updatescount2 (S109). The CPU 41 returns the processing to S99.

The processing is repeated and when the number of character codesincluded in ObjName is equal to or lower than count2, this means thatall of the ObjName has been checked. When the CPU 41 determines that thenumber of character codes included in ObjName is not larger than count2(no at S99), the CPU 41 ends the combined object value settingprocessing and returns the processing to the object data settingprocessing (refer to FIG. 14).

As shown in FIG. 14, after ending the combined object value settingprocessing (S73), the CPU 41 sets Result as the “object information[count1]. object data” (S75). The CPU 41 advances the processing to S79.

When the flag information “−1” is stored, the CPU 41 determines that theobject corresponding to the object information [count1] is not thecombined object (no at S71). In this case, the CPU 41 sets CSV [Rnum][field ID included in the object information [count1]] as “objectinformation [count1]. object data” (S77). The CPU 41 advances theprocessing to S79.

When the CPU 41 determines that the field ID is not included (no atS65), the CPU 41 sets the initial value included in the objectinformation [count1] as “object information [count1]. object data”(S69). The CPU 41 advances the processing to S79.

The CPU 41 adds “1” to count1 and updates count1 (S79). The CPU 41returns the processing to S63.

When the processing is repeated and the number of the pieces of objectinformation is equal to or lower than count1, this means that theabove-described processing has been performed with respect to all of thepieces of object information [0] to [N−1]. In this case, by theprocessing at S69, S75 and S77, a state is obtained in which the objectdata extracted from the record of the row number Rnum of the CSV filehas been set for each of the “object information [0]. object data” tothe “object information [N−1]. object data”. When the CPU 41 determinesthat the number of pieces of object information is not larger thancount1 (no at S63), the CPU 41 ends the object data setting processingand returns the processing to the DB load processing (refer to FIG. 13).As shown in FIG. 13, after ending the object data setting processing(S57), the CPU 41 returns the processing to the template switchingprocessing (refer to FIG. 11). As shown in FIG. 11, after ending the DBload processing (S35), the CPU 41 ends the template switching processingand returns the processing to the printer-side third main processing(refer to FIG. 10).

As shown in FIG. 10, after ending the template switching processing(S23), the CPU 41 sets idle “0” as the state information (S25). The CPU41 performs main editing processing (refer to FIG. 17) (S27).

The main editing processing will be explained with reference to FIG. 17.In the main editing processing, the editing screen 60 is switched inaccordance with an operation by the user, and editing of the CSV file isperformed. Further, print processing is performed based on the “objectinformation [0]. object data” to the “object information [N−1]. objectdata”.

The CPU 41 determines whether or not idle “0” is set as the stateinformation (S111). When the CPU 41 determines that idle “0” is set asthe state information (yes at S111), the CPU 41 performs idle screenprocessing (refer to FIG. 18) (S113). The idle screen processing will bedescribed in detail later. After ending the idle screen processing, theCPU 41 advances the processing to S127.

When the CPU 41 determines that record selection “1” is set as the stateinformation (no at S111; yes at S115), the CPU 41 performs recordselection screen processing (refer to FIG. 19) (S117). The recordselection screen processing will be described in detail later. Afterending the record selection screen processing, the CPU 41 advances theprocessing to S127.

When the CPU 41 determines that field selection “2” is set as the stateinformation (no at S115; yes at S119), the CPU 41 performs fieldselection screen processing (refer to FIG. 20) (S121). The fieldselection screen processing will be described in detail later. Afterending the field selection screen processing, the CPU 41 advances theprocessing to S127.

When the CPU 41 determines that object editing “3” is set as the stateinformation (no at S119; yes at S123), the CPU 41 performs objectediting screen processing (refer to FIG. 21) (S125). The object editingscreen processing will be described in detail later. After ending theobject editing screen processing, the CPU 41 advances the processing toS127. When the CPU 41 determines that a value other than “0” to “3” isset as the state information (no at S123), the CPU 41 advances theprocessing to S127.

The CPU 41 determines whether or not an operation to end the editing ofthe CSV file has been performed via the input portion 46 (S127). Whenthe CPU 41 determines that the operation to end the editing has not beenperformed (no at S127), the CPU 41 returns the processing to S111. Whenthe CPU 41 determines that the operation to end the editing has beenperformed (yes at S127), the CPU 41 returns the processing to theprinter-side third main processing (refer to FIG. 10). As shown in FIG.10, after ending the main editing processing (S27), the CPU 41 ends theprinter-side third main processing.

The idle screen processing will be explained with reference to FIG. 18.In the idle screen processing, when a touch operation is performed in astate in which the idle screen 61 (refer to FIG. 5) is displayed,corresponding processing is performed. The CPU 41 determines whether ornot the “DOWN” button has been touched (S131). When the CPU 41determines that the “DOWN” button has been touched (yes at S131), theCPU 41 adds “1” to Tnum (S135). The CPU 41 determines whether or notTnum is larger than a total number of the pieces of template data storedin the flash ROM 43 (S137). When the CPU 41 determines that Tnum islarger than the total number of the pieces of template data (yes atS137), the CPU 41 sets the total number of the pieces of template dataas Tnum, so that Tnum does not exceed the total number of the pieces oftemplate data (S139). The CPU 41 advances the processing to S141.

The CPU 41 determines whether or not the “UP” button has been touched(no at S131; S143). When the CPU 41 determines that the “UP” button hasbeen touched (yes at S143), the CPU 41 subtracts “1” from Tnum (S145).The CPU 41 determines whether or not Tnum is “0” (S147). When the CPU 41determines that Tnum is “0” (yes at S147), the CPU 41 sets Tnum to “1”so that Tnum is constantly equal to or greater than “1” (S149). The CPU41 advances the processing to S141. When the CPU 41 determines that Tnumis not “0” (no at S147), the CPU 41 advances the processing to S141.

Based on Tnum after the updating, the CPU 41 acquires the template data[Tnum] and performs the template switching processing (refer to FIG. 11)in order to acquire the object data (the “object information [0]. objectdata” to the “object information [N−1]. object data”) respectivelycorresponding to the object information [0] to [N−1] of the templatedata [Tnum] from the CSV file (S141).

The template switching processing is the same as the template switchingprocessing performed by the processing at S23 (refer to FIG. 10) and adetailed explanation thereof is therefore omitted here. By the templateswitching processing, the template data [Tnum] of Tnum after theupdating is read out from the flash ROM 43 and is stored in the RAM 42.Further, the object data extracted from the record [Rnum] of the CSVfile are set for each of the “object information [0]. object data” tothe “object information [N−1]. object data”. The CPU 41 ends the idlescreen processing and returns the processing to the main editingprocessing (refer to FIG. 17).

The CPU 41 determines whether or not the “OK” button has been touched(no at S143; S151). When the CPU 41 determines that the “OK” button hasbeen touched (yes at S151), the CPU 41 sets record selection “1” as thestate information (S153). The CPU 41 ends the idle screen processing andreturns the processing to the main editing processing (refer to FIG.17).

The CPU 41 determines whether or not the “PRINT” button has been touched(no at S151; S155). When the CPU 41 determines that the “PRINT” buttonhas been touched (yes at S155), the CPU 41 generates the print image inwhich each of the “object information [0]. object data” to the “objectinformation [N−1]. object data” are arranged based on thearrangement/size/font in accordance with the category of each of thecorresponding object information [0] to [N−1]. At that time, forexample, for the object data for which the category is “barcode,” abarcode indicating the corresponding object data (the combined objectdata) is generated and arranged. The CPU 41 prints the generated printimage onto the tape (S157). The CPU 41 ends the idle screen processingand returns the processing to the main editing processing (refer to FIG.17).

When the CPU 41 determines that the “PRINT” button has not been touched(no at S155), the CPU 41 ends the idle screen processing and returns theprocessing to the main editing processing (refer to FIG. 17).

The record selection screen processing will be explained with referenceto FIG. 19. In the record selection screen processing, when a touchoperation is performed in a state in which the record selection screen62 (refer to FIG. 5) is displayed, corresponding processing isperformed. The CPU 41 determines whether or not the “DOWN” button hasbeen touched (S161). When the CPU 41 determines that the “DOWN” buttonhas been touched (yes at S161), the CPU 41 adds “1” to Rnum (S165). TheCPU 41 determines whether or not Rnum is larger than a total number ofthe records of the CSV file stored in the flash ROM 43 (S167). When theCPU 41 determines that Rnum is larger than the total number of records(yes at S167), the CPU 41 sets the total number of records as Rnum, sothat Rnum does not exceed the total number of records (S169). The CPU 41advances the processing to S171.

The CPU 41 determines whether or not the “UP” button has been touched(no at S161; S173). When the CPU 41 determines that the “UP” button hasbeen touched (yes at S173), the CPU 41 subtracts “1” from Rnum (S175).The CPU 41 determines whether or not Rnum is “0” (S177). When the CPU 41determines that Rnum is “0” (yes at S177), the CPU 41 sets Rnum to “1”so that Rnum is constantly equal to or greater than “1” (S179). The CPU41 advances the processing to S171. When the CPU 41 determines that Rnumis not “0” (no at S177), the CPU 41 advances the processing to S171.

The CPU 41 performs the DB load processing (refer to FIG. 13) in orderto acquire the object data corresponding to the field IDs included ineach of the pieces of object information [0] to [N−1] of the templatedata [Tnum], of the data of the record [Rnum] of the CSV file (S171).

The DB load processing is the same as the DB load processing performedby the processing at S35 (refer to FIG. 11) and a detailed explanationthereof is therefore omitted here. By the DB load processing, the objectdata extracted from the record [Rnum] of the CSV file are set for eachof the “object information [0]. object data” to the “object information[N−1]. object data”. The CPU 41 ends the DB load processing, and afterthat returns the processing to the main editing processing (refer toFIG. 17).

The CPU 41 determines whether or not the “OK” button has been touched(no at S173; S181). When the CPU 41 determines that the “OK” button hasbeen touched (yes at S181), the CPU 41 sets field selection “2” as thestate information (S183). The CPU 41 ends the DB load processing andreturns the processing to the main editing processing (refer to FIG.17).

The CPU 41 determines whether or not the “BACK” button has been touched(no at S181; S189). When the CPU 41 determines that the “BACK” buttonhas been touched (yes at S189), the CPU 41 sets idle “0” as the stateinformation (S191). The CPU 41 ends the record selection screenprocessing and returns the processing to the main editing processing(refer to FIG. 17).

The CPU 41 determines whether or not the “PRINT” button has been touched(no at S189; S185). When the CPU 41 determines that the “PRINT” buttonhas been touched (yes at S185), the CPU 41 generates the print imagebased on each of the “object information [0]. object data” to the“object information [N−1]. object data”. The CPU 41 prints the generatedprint image on the tape (S187). The CPU 41 ends the record selectionscreen processing and returns the processing to the main editingprocessing (refer to FIG. 17).

When the CPU 41 determines that the “PRINT” button has not been touched(no at S185), the CPU 41 ends the record selection screen processing andreturns the processing to the main editing processing (refer to FIG.17).

The field selection screen processing will be explained with referenceto FIG. 20. In the field selection screen processing, when a touchoperation is performed in a state in which the field selection screen 63(refer to FIG. 5) is displayed, corresponding processing is performed.The CPU 41 determines whether or not the “DOWN” button has been touched(S201). When the CPU 41 determines that the “DOWN” button has beentouched (yes at S201), the CPU 41 adds “1” to ObjNum (S205). The CPU 41determines whether or not ObjNum is larger than a total number of thefields (S207). When the CPU 41 determines that ObjNum is larger than thetotal number of fields (yes at S207), the CPU 41 sets the total numberof fields as ObjNum, so that ObjNum does not exceed the total number ofthe fields (S209). The CPU 41 ends the field selection screen processingand returns the processing to the main editing processing (refer to FIG.17). When the CPU 41 determines that ObjNum is not larger than the totalnumber of fields (no at S207), the CPU 41 ends the field selectionscreen processing and returns the processing to the main editingprocessing (refer to FIG. 17).

The CPU 41 determines whether or not the “UP” button has been touched(no at S201; S213). When the CPU 41 determines that the “UP” button hasbeen touched (yes at S213), the CPU 41 subtracts “1” from ObjNum (S215).The CPU 41 determines whether or not ObjNum is “0” (S217). When the CPU41 determines that ObjNum is “0” (yes at S217), the CPU 41 sets ObjNumto “1” so that ObjNum is constantly equal to or greater than “1” (S219).The CPU 41 ends the field selection screen processing and returns theprocessing to the main editing processing (refer to FIG. 17). When theCPU 41 determines that ObjNum is not “0” (no at S217), the CPU 41 endsthe field selection screen processing and returns the processing to themain editing processing (refer to FIG. 17).

The CPU 41 determines whether or not the “OK” button has been touched(no at S231; S221). When the CPU 41 determines that the “OK” button hasbeen touched (yes at S221), the CPU 41 sets the object data of CSV[Rnum] [ObjNum] to TempValue (S222). Note that the reason for settingthe object data of CSV [Rnum] [ObjNum] to TempValue is to inhibit asituation in which a value is not set in TempValue when the “OK” buttonis touched when no input operation has been performed in object editingscreen processing (refer to FIG. 21) that will be explained later. TheCPU 41 sets object editing selection “3” as the state information(S223). The CPU 41 ends the field selection screen processing andreturns the processing to the main editing processing (refer to FIG.17).

The CPU 41 determines whether or not the “BACK” button has been touched(no at S221; S229). When the CPU 41 determines that the “BACK” buttonhas been touched (yes at S229), the CPU 41 sets record selection “1” asthe state information (S231). The CPU 41 ends the field selection screenprocessing and returns the processing to the main editing processing(refer to FIG. 17).

The CPU 41 determines whether or not the “PRINT” button has been touched(no at S229; S225). When the CPU 41 determines that the “PRINT” buttonhas been touched (yes at S225), the CPU 41 generates the print imagebased on each of the “object information [0]. object data” to the“object information [N−1]. object data”. The CPU 41 prints the generatedprint image on the tape (S227). The CPU 41 ends the field selectionscreen processing and returns the processing to the main editingprocessing (refer to FIG. 17).

When the CPU 41 determines that the “PRINT” button has not been touched(no at S225), the CPU 41 ends the field selection screen processing andreturns the processing to the main editing processing (refer to FIG.17).

The object editing screen processing will be explained with reference toFIG. 21. In the object editing screen processing, when a touch operationis performed in a state in which the object editing screen 64 (refer toFIG. 5) is displayed, corresponding processing is performed. The CPU 41determines whether or not the ten-key buttons have been touched (S232).When the CPU 41 determines that the ten-key buttons have been touched(yes at S232), the CPU 41 identifies a value that is input, based on thetouched ten-key button. The CPU 41 sets the input value as TempValue(S233). The CPU 41 ends the object editing screen processing and returnsthe processing to the main editing processing (refer to FIG. 17).

The CPU 41 determines whether or not the “OK” button has been touched(no at S232; S235). When the CPU 41 determines that the “OK” button hasbeen touched (yes at S235), the CPU 41 performs data editing processing(refer to FIG. 22) that edits CSV [Rnum] [ObjNum], based on the valueset as TempValue (S237).

The data editing processing will be explained with reference to FIG. 22.The CPU 41 updates CSV [Rnum] [ObjNum] to the input TempValue (S250).The CPU 41 determines whether or not the field ID that is the same asObjNum is included in one of the pieces of object information [0] to[N−1] of the template data [Tnum]. When the field ID that is the same asObjNum is included, the CPU 41 performs the combined object checkprocessing (refer to FIG. 15), in order to determine, based on theobject name, whether or not the corresponding object is the combinedobject (S251). The object name of the object information in which thefield ID that is the same as ObjNum is included is set as a parameterfor the combined object check processing.

It should be noted that when the field ID that is the same as ObjNum isnot included in one of the pieces of object information [0] to [N−1]included in the template data [Tnum], the CPU 41 sets “0” as theparameter for the combined object check processing.

The combined object check processing is the same as the combined objectcheck processing performed by the processing at S67 (refer to FIG. 14)and an explanation thereof is therefore omitted here. When it isdetermined by the combined object check processing that it is thecombined object, “0” is stored for the flag information in the RAM 42.When it is determined that it is not the combined object, “−1” is storedfor the flag information in the RAM 42. Note that, when “0” is set asthe parameter of the combined object check processing, “−1” is storedfor the flag information in the RAM 42, by the combined object checkprocessing.

After the combined object check processing (S251), the CPU 41 determineswhether or not it is the combined object, based on the flag informationstored in the RAM 42 (S253). When it is the combined object, this meansthat CSV [Rnum] [ObjNum] updated by the processing at S250 based on theTempValue is the combined object data. In this case, it is necessary toalso edit the single object data that is the basis of the combinedobject data. When the CPU 41 determines that it is the combined object(yes at S253), the CPU 41 performs the combined object editingprocessing (refer to FIG. 23), in order to edit the single object datathat is the basis of the combined object data (S255). The object name ofthe object information in which the field ID that is the same as ObjNumis included is set as a parameter of the combined object editingprocessing.

The combined object editing processing will be explained with referenceto FIG. 23. The CPU 41 sets the character code of the object name of theparameter as ObjName (S273). The CPU 41 deletes the character code“0x5F” of the “_” at the start and the end of ObjName (S275). The CPU 41sets count3 to “0” (S277). The CPU 41 determines whether or not a numberof character codes included in ObjName is greater than count3 (S279).When the CPU 41 determines that the number of character codes includedin ObjName is greater than count3 (yes at S279), the CPU 41 advances theprocessing to S281.

The CPU 41 sets the character code of “count3” of ObjName (hereinafterreferred to as ObjName(count3)) as Char (S281). When the same charactercode as the character code of ObjName(count3) continues from“count3+1”th onward, the CPU 41 identifies the continuous number. TheCPU 41 sets the identified continuous number as Digit (S283). The CPU 41subtracts the character code “0x41” of “A” from Char. The CPU 41 sets aresult of the subtraction as FiedNum (S285).

Of TempValue, the CPU 41 extracts, from the character code of“count3”th, a character code corresponding to the number of digits ofDigit. The CPU 41 sets the extracted character code as fval (S289). TheCPU 41 performs specific field replacement processing (refer to FIG.24), in order to edit the single object data that is the basis of thecombined object data using fval (S291).

The specific field replacement processing will be explained withreference to FIG. 24. The CPU 41 sets count4 to “0” (S301). The CPU 41determines whether or not the number N of the pieces of objectinformation [0] to [N−1] included in the template data [Tnum] is largerthan count4 (S303). When the CPU 41 determines that the number N of thepieces of object information [0] to [N−1] is larger than count4 (yes atS303), the CPU 41 determines whether or not the field ID of the objectinformation [count4] is the same as FiedNum (S305). When the field ID ofthe object information [count4] is the same as FiedNum, this means thatthe object corresponding to the object information [count4] is thesingle object that is the basis of the combined object. When the CPU 41determines that the field ID of the object information [count4] is thesame as FiedNum (yes at S305), the CPU 41 sets fval as “objectinformation [count4]. object data” (S307). In this way, the singleobject data that is the basis of the combined object data is changed ina similar manner, in accordance with the updating of the combined objectdata. The CPU 41 sets fval as CSV [Rnum] [FiedNum] (S308). The CPU 41advances the processing to S309. When the CPU 41 determines that thefield ID of the object information [count4] is not the same as FiedNum(no at S305), the CPU 41 advances the processing to S309.

The CPU 41 adds “1” to count4 and updates count4 (S309). The CPU 41returns the processing to S303. When the CPU 41 determines that thenumber of the pieces of object information is not larger than count4 (noat S303), this means that the CPU 41 has performed the above-describedprocessing with respect to all of the pieces of object information [0]to [N−1]. In other words, of the plurality of single object data thatform the basis of the combined object data, all of the single objectdata that need to be updated in accordance with the updating of thecombined object data have been updated. The CPU 41 ends the specificfield replacement processing and returns the processing to the combinedobject editing processing (refer to FIG. 23).

As shown in FIG. 23, after ending the specific field replacementprocessing (S291), the CPU 41 adds Digit to count3 and updates count3(S293). The CPU 41 returns the processing to S279.

When the processing is repeated and the number of character codesincluded in ObjName is equal to or lower than count3, this means thatthe above-described processing has been performed with respect to all ofthe object names. When the CPU 41 determines that the number ofcharacter codes included in ObjName is not larger than count3 (no atS279), TempValue is associated with object information [ ] that includesthe same field ID as ObjNum and is stored in the RAM 42. In other words,TempValue is set as “object information [(object information indexincluding same field ID as ObjNum)]. object data” (S295). The CPU 41ends the combined object editing processing and returns the processingto the data editing processing (refer to FIG. 22). As shown in FIG. 22,after the CPU 41 ends the data editing processing (S255), the CPU 41returns the processing to the object editing screen processing (refer toFIG. 21).

On the other hand, when it is determined by the combined object checkprocessing (S251) that it is not the combined object, this means thatthe editing target CSV [Rnum] [ObjNum] is the single object data. Inthis case, when there is the combined object data that is generatedbased on the editing target CSV [Rnum] [ObjNum], it is necessary to alsoedit the combined object data. When the CPU 41 determines that it is notthe combined object (no at S253), in order to also edit the combinedobject data, the CPU 41 performs combined object search/replacementprocessing (refer to FIG. 25) (S259).

The combined object search/replacement processing will be explained withreference to FIG. 25. The CPU 41 sets count5 to “0” and thus initializescount5 (S311). The CPU 41 determines whether or not the number N of thepieces of object information [0] to [N−1] included in the template data[Tnum] is larger than count5 (S313). When the CPU 41 determines that thenumber N of the pieces of object information [0] to [N−1] is larger thancount5 (yes at S313), the CPU 41 performs the combined object checkprocessing (refer to FIG. 15), in order to determine whether the objectcorresponding to the object information [count5] is the combined object,based on the object name (S315). The object name included in the objectinformation [count5] is set as a parameter for the combined object checkprocessing. The combined object check processing is the same as thecombined object check processing performed by the processing at S67(refer to FIG. 14) and an explanation thereof is therefore omitted here.

After the combined object check processing (S315), the CPU 41 determineswhether or not it is the combined object, based on the flag informationstored in the RAM 42 (S317). When the CPU 41 determines that it is notthe combined object (no at S317), the CPU 41 advances the processing toS321.

Meanwhile, when the object corresponding to the object information[count5] is the combined object, it is possible that CSV [Rnum] [ObjNum]is included among the plurality of single object data that form thebasis of the combined object data. In this case, it is necessary to alsoedit the combined object data, in accordance with the updating of CSV[Rnum] [ObjNum] using TempValue. When the CPU 41 determines that it isthe combined object (yes at S317), the CPU 41 performs combined objectvalue replacement processing (refer to FIG. 26), in order to edit thecombined object data as necessary (S319). The object name included inthe object information [count5] and the field ID included in the objectinformation [count5] are set as parameters of the combined object valuereplacement processing.

The combined object value replacement processing will be explained withreference to FIG. 26. The CPU 41 sets the character code of the objectname of the parameter as ObjName (S333). The CPU 41 sets the field ID ofthe parameter as Fnum (S334). The CPU 41 deletes the character code“0x5F” of the “_” at the start and the end of ObjName (S335). The CPU 41sets a variable count6 to “0” (S337). The CPU 41 determines whether ornot a number of character codes included in ObjName is greater thancount6 (S339). When the CPU 41 determines that the number of charactercodes included in ObjName is greater than count6 (yes at S339), the CPU41 advances the processing to S341.

The CPU 41 sets the character code of “count6”th of ObjName (hereinafterreferred to as ObjName(count6)) as Char (S341). When the same charactercode as the character code of ObjName(count6) continues from“count6+1”th onward, the CPU 41 identifies the continuous number. TheCPU 41 sets the identified continuous number as Digit (S343). The CPU 41subtracts the character code “0x41” of “A” from Char. The CPU 41 sets aresult of the subtraction as FiedNum (S345).

The CPU 41 determines whether or not FiedNum and Fnum match each other(S347). When FiedNum and Fnum match each other, this means that it isnecessary to update the combined object data corresponding to the objectinformation [count5] in accordance with the updating, using TempValue,of the single object data that is the basis of the combined object data.When the CPU 41 determines that FiedNum and Fnum match each other (yesat S347), of the “object information [count5]. object data”, the CPU 41stores TempValue as the value corresponding to the number of digits ofDigit from the character code of “count6”th (S349). Of CSV [Rnum][Fnum], the CPU 41 stores TempValue as the value corresponding to thenumber of digits of Digit from the character code of “count6”th (S350).The CPU 41 advances the processing to S353. When the CPU 41 determinesthat FiedNum and Fnum do not match each other (no at S347), the CPU 41advances the processing to S353.

The CPU 41 adds Digit to count6 and updates count6 (S353). The CPU 41returns the processing to S339. When the processing is repeated and thenumber of character codes included in ObjName is equal to or lower thancount6, this means that the above-described processing has beenperformed with respect to all of the object names. When the CPU 41determines that the number of character codes included in ObjName is notlarger than count6 (no at S339), the CPU 41 ends the combined objectvalue replacement processing and returns the processing to the combinedobject search/replacement processing (refer to FIG. 25). As shown inFIG. 25, after the combined object value replacement processing (S319),the CPU 41 advances the processing to S321.

The CPU 41 adds “1” to count5 and updates count5 (S321). The CPU 41returns the processing to S313. When the processing is repeated and thenumber N of the pieces of object information [0] to [N−1] is equal to orlower than count5, this means that the above-described processing hasbeen performed with respect to all of the pieces of object information[0] to [N−1]. When the CPU 41 determines that the number N of the piecesof object information [0] to [N−1] is not larger than count5 (no atS313), the CPU 41 ends the combined object search/replacement processingand returns the processing to the data editing processing (refer to FIG.22). As shown in FIG. 22, after ending the combined objectsearch/replacement processing (S259), the CPU 41 ends the data editingprocessing and returns the processing to the object editing screenprocessing (refer to FIG. 21).

As shown in FIG. 21, after ending the data editing processing (S237),the CPU 41 sets field selection “2” as the state information (S239). TheCPU 41 ends the object editing screen processing and returns theprocessing to the main editing processing (refer to FIG. 17).

The CPU 41 determines whether or not the “BACK” button has been touched(no at S235; S241). When the CPU 41 determines that the “BACK” buttonhas been touched (yes at S241), the CPU 41 sets field selection “2” asthe state information (S243). The CPU 41 ends the object editing screenprocessing and returns the processing to the main editing processing(refer to FIG. 17). When the CPU 41 determines that the “BACK” buttonhas not been touched (no at S241), the CPU 41 ends the object editingscreen processing and returns the processing to the main editingprocessing (refer to FIG. 17).

As explained above, when the object name has “_” at the start and theend, the CPU 41 of the printer 4 determines that the object data of thecorresponding object is the combined object. The CPU 41 selects two ormore of the single object data from the plurality of single object dataof the CSV file (S106). The CPU 41 generates the combined object data bycombining the selected two or more object data (S107). Therefore, theCPU 41 can generate the combined object data based on the object name.The CPU 41 can print the print image based on the generated combinedobject data (S157, S187, S227). Thus, the CPU 41 can easily perform theprinting based on the combined object data, without requiring a settingoperation by the user.

There is a case in which at least one of the plurality of single objectdata that form the basis of the combined object data is updated (S250).In this case, the CPU 41 changes a section of the combined object datathat corresponds to the updated single object data using the same changecontent, and thus changes the combined object data (S349). In thismanner, when the user has changed the single object data, it is possibleto omit an effort to change the combined object data at the same time.As a result, the user can easily change the single object data and thecombined object data.

There is a case in which the combined object data is changed (S250). Inthis case, the CPU 41 can change the single object data that form thebasis of the changed combined object data, using the same change content(S307). In this way, when the user has changed the combined object data,it is possible to omit an effort to change the single object data thatform the basis of the combined object data at the same time. Thus, theuser can easily change the single object data and the combined objectdata.

Depending on whether or not “_” is included at the start and the end ofthe object name, the CPU 41 determines whether or not the objectcorresponding to the object name is the single object or the combinedobject (S81). In this case, the CPU 41 can easily distinguish whether ornot it is the object name of the combined object.

In the object name of the combined object, field IDs “A,” “B” . . . , offields in which the single object data that form the basis of thecombined object data are stored, are arranged sequentially. The CPU 41can generate the combined object data by combining the single objectdata of the fields corresponding to the field IDs in the order of thefield IDs. As a result, the CPU 41 can easily generate the combinedobject data based on the field IDs included in the object name and theirorder.

The CPU 41 can create a barcode based on the combined object data of thefield ID “E” and can print the print image that includes the barcode.The printer 4 can print the barcode showing the two or more selectedobject data selected based on the object name from among the pluralityof single object data, onto a print medium, based on the combined objectdata.

The present disclosure is not limited to the above-described embodiment,and various modifications are possible. With respect to theabove-described embodiment, “_” that is added to the start and the endof the object name in order to indicate that it is the object name ofthe combined object may be another predetermined code. Alternatively,the predetermined code may be added to only the start or the end of theobject name. Further, the predetermined code may be included in asection of the object name other than the start and the end.

The fact that the object name is the object name of the combined objectmay be indicated using a method other than that of adding thepredetermined code. For example, it may be indicated that it is thecombined object data by including, in the object name, a desired codethat continues for a predetermined number (10, for example) of digits ormore.

In the above-described embodiment, the number of digits of the singleobject data that forms the basis of the combined object data isdetermined in accordance with the continuous number of the field IDincluded in the object name. The number of digits of the single objectdata may be represented using numerals. For example, an object name“_AABBBBBCCCCC_” in the above-described embodiment may be represented by“_A2B5C5_”. Note that the numerals included in the object name representthe number of digits of the single object data of the immediatelypreceding field ID. In the case of the above-described object name, theobject name shows that the single object data of the field ID “A” is twodigits, the single object data of the field ID “B” is 5 digits and thesingle object data of the field ID “C” is 5 digits.

When “#” is included in the object name, a check digit may be added to acorresponding position, of the combined object data.

In the above-described embodiment, the combined object data (thecombined object data of the field ID “E” as shown in FIG. 2, forexample) is included in the CSV file transmitted from the PC 5 to theprinter 4. In contrast to this, the PC 5 may transmit the CSV file thatdoes not include the combined object data to the printer 4. Based on theobject name of the object information, the CPU 41 of the printer 4 maydetermine whether or not it is the combined object, using the samemethod as that described above. When the CPU 41 determines that it isthe combined object, the CPU 41 may generate the combined object data bycombining the plurality of single object data that form the basis of thecombined object data. The CPU 41 may newly store, in the CSV file, thegenerated combined object data, as the combined object data of the fieldIDs included in the corresponding object information.

The apparatus and methods described above with reference to the variousembodiments are merely examples. It goes without saying that they arenot confined to the depicted embodiments. While various features havebeen described in conjunction with the examples outlined above, variousalternatives, modifications, variations, and/or improvements of thosefeatures and/or examples may be possible. Accordingly, the examples, asset forth above, are intended to be illustrative. Various changes may bemade without departing from the broad spirit and scope of the underlyingprinciples.

What is claimed is:
 1. A printer electrically connectable to an externaldevice to receive data and including a print mechanism installed to forma print image on a print medium based on a plurality of object datareceived from the external device, the print image having a plurality ofobjects, each of the plurality of objects respectively corresponding toa different one of the plurality of object data, the printer comprising:a memory configured to store at least the plurality of object data; anda processor electrically connected to the memory and the print mechanismto control a storing state of the memory and operation of the printmechanism, the processor configured to perform processes comprising:storing, in the memory, a database file linked to a template data basedon the plurality of the object data received from the external device,the database file including a record including a plurality of objectdata each of which is associated with one of a plurality of fields, therecord including a first object data associated with a first field outof the plurality of the fields and corresponding to a first object, asecond object data associated with a second field out of the pluralityof the fields, and a third object data associated with a third field outof the plurality of the fields and corresponding to a combined object,the combined object being an object to be formed in the print image, thethird object data being a combined data generated by arranging the firstobject data and the second object data in order, the record includingthe first object data, the second object data, and the third objectdata, the template data being a data received from the external deviceand stored in the memory and including a combined object name and aplurality of field identifiers, a first field identifier, of theplurality of the field identifiers, corresponding to a first characterand associated with the first field, and a second field identifier, ofthe plurality of the field identifiers, corresponding to a secondcharacter different from the first character and associated with thesecond field, the combined object name associated with the combinedobject, the combined object name including at least one of the firstcharacters having a first number of digits and at least one of thesecond characters having a second number of digits, the first numbercorresponding to a number of digits of the first object data, the secondnumber corresponding to a number of digits of the second object data,each of the at least one of the first characters being a same character,each of the at least one of the second characters being a same characterdifferent from each of the at least one of the first characters, and theat least one of the first characters and the at least one of the secondcharacters being arranged in order; and obtaining a template; insertingthe third object data into the template; and controlling the printmechanism to form the print image including the template with the firstobject and the combined object based on the template data and the thirdobject data.
 2. The printer according to claim 1, wherein the processoris configured to perform processes further comprising: first changingthe first object data; and second changing the third object data inaccordance with the first changing, by changing a part, whichcorresponds to the first object data, of the third object data based onthe combined object name and the first character corresponding to thefirst field identifier, the first field identifier associated with thefirst object data.
 3. The printer according to claim 2, wherein theprocessor is configured to perform processes further comprising: thirdchanging a part, which corresponds to the first object data, of thethird object data; and fourth changing the first object data inaccordance with the third changing, based on the combined object nameand the first character corresponding to the first field identifier, thefirst field identifier associated with the first object data.
 4. Theprinter according to claim 1, wherein the combined object name includesa specified character code being different from the first character andthe second character.
 5. The printer according to claim 1, wherein theprint image includes a barcode that is the combined object correspondingto the third object data.
 6. The printer according to claim 4, whereinthe combined object name starts or ends with the specified charactercode.
 7. A printer electrically connectable to an external device toreceive data and including a print mechanism installed to form a printimage on a print medium based on a plurality of object data receivedfrom the external device, the print image having a plurality of objects,each of the plurality of objects respectively corresponding to adifferent one of the plurality of object data, the printer comprising: amemory configured to store at least the plurality of object data; and aprocessor electrically connected to the memory and the print mechanismto control a storing state of the memory and operation of the printmechanism, the processor configured to perform processes comprising:storing, in the memory, a database file linked to a template data basedon the plurality of the object data received from the external device,the database file including a record including a plurality of objectdata each of which is associated with one of a plurality of fields, therecord including a first object data associated with a first field outof the plurality of the fields and corresponding to a first object, asecond object data associated with a second field out of the pluralityof the fields, and a third object data associated with a third field outof the plurality of the fields and corresponding to a combined object,the combined object being an object to be formed in the print image, thethird object data being a combined data generated by arranging the firstobject data and the second object data in order, the record includingthe first object data, the second object data, and the third objectdata, the template data being a data received from the external deviceand stored in the memory and including an object name and a plurality offield identifiers, a first field identifier, out of the plurality of thefield identifiers, corresponding to a first character and associatedwith the first field, and a second field identifier, out of theplurality of the field identifiers, corresponding to a second characterdifferent from the first character and associated with the second field,the object name associated with the combined object, the object nameincluding one character of the first character, a first number, onecharacter of the second character, and a second number, the first numbercorresponding to a number of digits of the first object data, and thesecond number corresponding to a number of digits of the second objectdata, and the one character of the first character, the first number,the one character of the second character, and the second number beingarranged in order; and controlling the print mechanism to form the printimage including the first object and the combined object based on thetemplate data and the third object data.
 8. The printer according toclaim 7, wherein the processor is configured to perform processesfurther comprising: first changing the first object data; and secondchanging the third object data in accordance with the first changing, bychanging a part, which corresponds to the first object data, of thethird object data based on the object name and the first charactercorresponding to the first field identifier, the first field identifierassociated with the first object data.
 9. The printer according to claim8, wherein the processor is configured to perform processes furthercomprising: third changing a part, which corresponds to the first objectdata, of the third object data; and fourth changing the first objectdata in accordance with the third changing, based on the object name andthe first character corresponding to the first field identifier, thefirst field identifier associated with the first object data.
 10. Theprinter according to claim 7, wherein the object name includes aspecified character code being different from the first character andthe second character.
 11. The printer according to claim 7, wherein theprint image includes a barcode that is the combined object correspondingto the third object data.
 12. The printer according to claim 10, whereinthe object name starts or ends with the specified character code.